Shareware Grab Bag/Shareware Grab Bag.iso/098/abbl16.arc/POLICY.TXT

Text File | 1988-02-02 | 7.8 KB | 141 lines

----- ATLANTA BULLETIN BOARD LIST -----
-------- POLICIES & PROCEDURES --------

      ABBL #16,  February 2, 1988
     By Tim Farley, OAS Secretary

Some  general notes on how the ABBL  is compiled  are included below.   If  you
have any questions about specific items or   specific  listings  in  the  ABBL,
please   feel  free  to   contact   the compilers   of   the   list.    Contact
information  is included at the end  of this file.

The  ABBL is maintained using a custom- designed    database   program    which
contains  all  the  relevant  info  and automatically  formats the  final  text
files.   All  information  is  verified every edition of the list.   Typically,
two  OAS  members  work  together,  one maintaining   the  database  and   both
making  numerous outgoing phone  calls, both   voice   and  data,   to   gather
information.

With all new systems,  and to a certain degree  on existing systems,  the  list
compilers do actually read bulletins  & messages online to determine the status
of  the  system and any updates to  the information in the list.   Much of  the
"comment"  information  in the list  is created  by  the  compilers  from  data
collected  this   way.    However,   we strongly  encourage  sysops to keep  in
touch  with  us  about  their  listing: with the large number of local  boards,
we  cannot  spend any large  amount  of time on each one.

In   addition,   a  highly  intelligent custom  communications program  written
by   Jim  Kloss  of  Nochange  Software assists  in  verification  of  existing
systems.   It  actually logs  into  the system,  and captures all notices which
appear on the screen,  keeping a log of the  progress  of all  outgoing  calls.
This  is not a "demon  dialer",  but  a highly    sophisticated   system   that
actually  understands how to log on  to most BBS programs as a new  user.  Over
2,500   outgoing  phone   calls,   both automated  and manual,  were  necessary
during  the verification of the  latest list.

Verifications  are usually done between the  third Thursday of the  month  (the
OAS  Business  Meeting) and the end  of the month,  for the list to be ready by
the first of each month.

VERIFICATION:

The  meaning of the verification  codes is  quite straightforward:   "V"  means
the  system  was verified  by  actually logging  on,  or  at least receiving  a
banner  or other welcoming  message  on the  screen.   "NN" indicates a  system
with   a  new  phone  number,   and  is equivalent  to  "V".    "B"  means  the
system  is  continually  shows  a  busy signal when called, even after repeated
attempts.  "NA" means either the system did not answer, or it presented carrier
but  would  not print anything  to  the screen.

NEW SYSTEMS:

NEW  systems  are  classified  as  just that,  not  a  system which  has  given
itself  a  new  name or  phone  number. (The   comment  fields  are   used   to
indicate  when a system has had a  name change, and the "NN" code indicates new
numbers.)  Any system not listed in the immediately  previous  edition  of  the
list  is  considered  new:   thus,  for various   reasons,   systems  could  be
online  many  months but  still  marked new.   New  systems are only marked  as
such  for one month.   New systems  are always  verified:  if we cannot log in,
the new system report is held until the next  month's list.   Although we  seek
out   new  board  reports  by   reading messages   on  systems  which  we   are
verifying,   we  encourage  sysops  and users  to report new systems when  they
encounter them.    Don't assume we know about it already!

Do note that the compilers of the  list reserve  the  right  not  to  list  any
NEW  system  not deemed stable  at  the time of verification.  Because the ABBL
is distributed nationally,  listing  of an  unstable system could cause no  end
of difficulty for the sysop and others, should  the system actually go down  or
have       persistent       operational difficulties.  Systems which are up for
arbitrarily  short  hours  (e.g.,  less than 4 hours per day), or require voice
contact  with the sysop for connection, or  are brand new and not  yet  stable,
may  fall into this  category.   Sysops are encouraged to contact the compilers
of the list if such a situation occurs. Most  times  the systems will  make  it
into the next months list,  after it is clear  that  the problems have  passed.
In  actual experience these  cases  are quite rare.

NOW DOWN:

If   a  previously  listed  system   is currently  down  due  to  hardware   or
software      problems     or     other difficulties, the phone number will not
be  printed but will be  replaced  with the  string "now down".   This prevents
unnecessary  phone  calls to  a  number that  may be changing,  but lets  users
know  that  the  system  still  exists. This  is only done after  contact  with
the  sysop,  so the exact situation  is known to the compilers.

DEAD SYSTEMS:

Systems  showing NO signs of  life  are considered  "dead".  Most  times  these
systems    have   had   their    phones disconnected,    or   changed   to   an
unpublished  number,   etc.   For  that reason,   the  phone  numbers  of  dead
systems are never printed.   Hopefully, most sysops will contact us or at least
give  some sort of public notice before taking their systems down.

Because  not all sysops keep in  touch, we  have to tag systems "dead" when  we
cannot  get in touch with them at  all. If  a system is "no answer" two  months
in  a  row,   it  is  tagged  as  dead. Likewise  for  continuous busy  signals
that persist despite repeated  dialing. We  realize that often this results  in
erroneous "dead" listings,  but usually readers  of  the list will point  these
out when they occur.  It is a necessary evil,  to prevent perpetually  unstable
systems  from  causing a great deal  of grief for users.

PRIVATE SYSTEMS:

Private   systems,    (i.e.    standard bulletin  board systems that  are  open
only  to a small segment of the  public or  by  personal  referral),   are  not
listed  although we keep information on them  in the database and  verify  them
every month.   Sysops need to notify us as  to  the status of their  system  if
they do not wish it to be listed.  Note that  even  though  a system  may  have
closed registration, or charge fees, it is  not  listed as private  unless  the
sysop indicates such,  or it is obvious from the system welcome that it is so.

"PIRATE" SYSTEMS

In     addition,     if     sufficient, reproducible   hard-copy  evidence   is
presented  to the list maintainers that a  system  is engaging in  the  illegal
distribution  of  copyrighted  software without the author's permission;  or in
the publication of credit card numbers, alternate long distance service  access
codes, or access information to private computer systems;  or in any other sort
of verifiable fraud or other violations of the laws of the United States and/or
the  State  of Georgia;  SUCH A  SYSTEM WILL  BE TAGGED AS PRIVATE  until  some
explanation  is  forthcoming  from  the system  operator.   We  do  not  remove
systems from this list frivolously,  as such action endangers the value of  the
list   as  an   information   resource. However,  we will not publicize systems
that are breaking the law, should we be able  to  prove that such is the  case.
Again,   this   is  only   done   after reproducible  evidence is presented  to
the list compilers (this information is kept  on file) and repeated attempts to
solicit  an explanation from the  sysop fail.

Please    direct   any   comments    or inquiries  about the  Atlanta  Bulletin
Board List to the following:

 Organization of Atlanta Sysops, Inc.
          Post Office Box 561
        Decatur, GA  30031-0561

             The OASis BBS
       [phone], 24 hours
      300/1200/2400/9600 USR HST

                 *end*